Repository navigation
[29.x backport] vendor: go.yaml.in/yaml/v3 v3.0.6 (security) - #7461
Merged
Merged
Conversation
resolve: hint-class literal merge-key string "<<" so it's quoted on encode full diff: yaml/go-yaml@v3.0.5...v3.0.6 Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 796f963) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
docker-agent
reviewed
Nov 3, 2026
docker-agent
left a comment
docker-agent
left a comment
Contributor
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
docker-agent
reviewed
Nov 3, 2026
docker-agent
left a comment
docker-agent
left a comment
Contributor
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
vvoland
approved these changes
Nov 3, 2026
docker-agent
reviewed
Nov 3, 2026
docker-agent
left a comment
docker-agent
left a comment
Contributor
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
3 tasks
berolinux
added a commit
to OpenMandrivaAssociation/docker-cli
that referenced
this pull request
Nov 4, 2026
Security release. The CLI vendors the go-jose, zstd, and SwarmKit fixes; overlay iptables and BuildKit are engine-side. CVE-2026-116587: excessive CPU when parsing crafted RSA keys (GHSA-mgcc-cww5-fp2q), via go-jose v4.1.7. CVE-2026-116591: panic when decompressing crafted zstd (GHSA-fpmh-frq8-7rj8), via klauspost/compress v1.20.2. CVE-2026-115538: Swarm overlay networks lose encryption and spoofing protection after firewalld flushes Docker's iptables rules (GHSA-6jhp-7446-hf7f). CVE-2026-115539: a worker TLS certificate can obtain a manager certificate after a Swarm leader change (GHSA-628g-hv7f-pgjc), vendored SwarmKit v2.1.3. BuildKit v0.34.2 (engine): CVE-2026-121522 (GHSA-2fqp-xg6f-v7gj): resolving the same Git source twice can crash the daemon through resolver cache poisoning. CVE-2026-121520 (GHSA-w26x-xg27-7qjc): a client with BuildKit control API access could set extended attributes outside the state directory. CLI: quote literal "<<" keys when emitting YAML so they are not decoded as merge keys (docker/cli#7461, go.yaml.in/yaml/v3 v3.0.6).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
vendor: go.yaml.in/yaml/v3 v3.0.6
resolve: hint-class literal merge-key string "<<" so it's quoted on encode
full diff: yaml/go-yaml@v3.0.5...v3.0.6
Release notes (optional)
A picture of a cute animal (not mandatory but encouraged)